Managing anonymous network connections

ABSTRACT

Managing anonymous network connections. In one aspect managing anonymous network connections by providing anonymous authentication credentials to a plurality of devices in a hierarchical network, registering a first set of devices at a first data aggregator, determining that the first set of devices at the first aggregator numbers less than a first threshold value, registering the first set of devices with a second aggregator upstream in the hierarchy from the first aggregator, causing data from the first set of devices to be received at the second aggregator.

BACKGROUND

The disclosure relates generally to aggregating data from anonymousnetworked devices. The disclosure relates particularly to managinganonymous network connections among Internet of Things devices connectedto edge cloud resources.

The proliferation of smart devices connected to the Internet of Things(IoT) including smart appliance, power meters and other smart devices inhomes, is accompanied by the creation of large quantities of data.Aggregating and analyzing this data could increase its value.

Anonymous credentials allow validated users to repeatedly access systemswithout sacrificing their privacy. Repeated connections by a single userare not linked to each other. Public Key Infrastructure can be enhancedwith Zero Knowledge Proof cryptography to build anonymous credentials.

SUMMARY

Aspects of the invention disclose methods, systems and computer readablemedia associated with managing anonymous network connections. In oneaspect managing anonymous network connections by providing anonymousauthentication credentials to a plurality of devices in a hierarchicalnetwork, registering a first set of devices at a first data aggregator,determining that the first set of devices at the first aggregatornumbers less than a first threshold value, registering the first set ofdevices with a second aggregator upstream in the hierarchy from thefirst aggregator, causing data from the first set of devices to bereceived at the second aggregator.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 provides a schematic illustration of a system, according to anembodiment of the invention.

FIG. 2 provides a flowchart depicting an operational sequence, accordingto an embodiment of the invention.

FIG. 3 depicts a generalized architecture of the system elements,according to an embodiment of the invention.

FIG. 4 depicts a cloud computing environment, according to an embodimentof the invention.

FIG. 5 depicts abstraction model layers, according to an embodiment ofthe invention.

DETAILED DESCRIPTION

Value can be added to IoT data through aggregation and analysis. MuchIoT data is personal in nature and the collection, aggregation andanalysis can raise data privacy concerns. Aggregated data can beanonymized, but aggregated and anonymized data can be de-anonymizedunder certain conditions. Aggregating data from anonymous devices canhelp protect device anonymity when data from a large enough number ofdevices is being aggregated. Aggregating data from too small a group ofdevices risks exposing the identity of the devices.

In an embodiment for aggregating data from anonymous networked devices,a plurality of new-to-the network individual devices are registered aspart of an IoT network. The initial connection and registration caninclude a manual component such as a phone call, text message, email, oronline registration process to provide information about the new deviceincluding location, ownership, etc. The connection can be a hardwiredconnection, or wireless connection using local wireless networktechnologies.

The network can be based upon geography where each successive level ofthe network hierarchy covers a larger geographic area than the lowerlevel, where the larger geographic area includes the area of the lowerlevels of the hierarchy. Local networks associated with a smallgeographic region can be consolidated into a next level networkincluding multiple local geographies, and regional networks consociatingthe next level networks and so on. The aggregators can be actualphysical system elements or virtual aggregators defined on computationalresources. For virtual aggregators, the same geographic limits can bedefined for specific network addresses residing on a common server.Reporting endpoints are initially directed to a “local” aggregator basedupon location information associated with the network hierarchyinformation carried in the device's credentials. As the devices need tomove up or down stream in the hierarchy, the credential's networkhierarchy is used to redirect the device to different aggregators.

Upon connecting, anonymous credentials are created by a centralizedissuing element, and issued to the new device. In an embodiment, theanonymous credentials can relate to the class of the device, utilitymeter, appliance, or other IoT device. The anonymous credentials caninclude location information of the device. In an embodiment, thecredentials include information regarding the aggregators for the deviceat multiple levels of the network hierarchy together with networkaddresses etc., for the respective aggregators. The anonymouscredentials can include Zero-Knowledge unlinkable attribute-basedcredentials, allowing each device to be anonymously validated incommunications with the network without repeated communications beingassociated with the device or each other. In an embodiment, theanonymous credentials of a disabled or inactive device can be revoked,preventing the device from reporting data.

In an embodiment, devices with credentials register with their localaggregator. The local aggregator verifies the credentials of the device.In an embodiment, the aggregator can cross-authenticate the device withall other reporting devices, ensuring that the device's credentials arevalid. In an embodiment, a zk-SNARK program can be used to validatedevices with appropriate credentials.

The local aggregator issues a session token to the registering device.In an embodiment, the session token of each device may be recorded in aregistry of tokens together with the encrypted identifier of the device.The identifiers can be encrypted using a public-private key pair. Keypairs can be associated with utility providers, public authorities andother entities. Utility providers can use their key pair to monitor alldevices serviced by the utility, but without identifying individualdevices. Public authorities can use their key to monitor individualdevices subject to legal protections of personal privacy and freedomfrom invasive searches without a warrant. In an embodiment, thecredential can be structured such that the utility and the publicauthorities must be cooperate to access identified individual devicelevel information. In an embodiment, the registry of tokens can bemaintained in a distributed ledger such as a blockchain ledger, or aprivate ledger including a private blockchain ledger.

In an embodiment, the device uses the session token to register witheach aggregator in its hierarchy beginning with the local aggregator andproceeding up through the hierarchy to the highest-level aggregator. Thelocal aggregator and provides the current number of devices reporting tothe aggregator. The device compares the current number of devices to itssecurity threshold—the minimum number of reporting devices which isacceptable to the device. The device begins reporting data toaggregators under conditions where the device plus the current number ofreporting devices meets or exceeds the security threshold. The securitythreshold can be zero or any positive integer. The security thresholdcan be uniform across the system, or can vary from device to device, bygeographic area, by device classification, or a combination of thesedimensions. The value can be fixed, set by the manufacturer, or by autility, or may be set to a default with an option for a user to changethe value. There can be an option for a user to disable reportingcompletely.

In an embodiment, endpoint devices continuously report data as long asthey are registered to an aggregator having a number of reportingdevices above the endpoint device's security threshold. In anembodiment, endpoint devices periodically (hourly, daily, weekly, etc.)report their data to a suitable aggregator.

In an embodiment, all endpoint devices are members of a single class andall report to a single set of aggregators. In an alternative embodiment,multiple device classes can be defined, electric meters, gas meters,smart appliances, smart thermostats, etc., all reporting to a single setof physical aggregators. In this embodiment, the level of aggregationcan vary by class, classes having populations above their securitythreshold can report to a low, local level aggregator while classeshaving a local population below their threshold can report to ahigher-level aggregator.

Under condition where the number of current reporting devices plus thenew device falls below the security threshold, the new device checks inwith the next level aggregator of the network. The device may havepreviously registered with a first level aggregator as described aboveor may register with the aggregator, using the anonymous credentials andsession token from the local aggregator, at this time. The second, ornext-level aggregator provides the device with the current number ofdevice reporting data and the device compares this value plus one, tothe security threshold. The device begins reporting data to thenext-level aggregator under conditions where the current number ofreporting devices plus the new device meets or exceeds the threshold.Under all other conditions, the device continues up the hierarchy untilan aggregator is found with enough currently reporting devices thatadding the new device will meet or exceed the security threshold of thedevice. In an embodiment, as or after the device begins reporting datato an appropriate aggregator, the device reports to each downstreamaggregator with which the device is registered using its session token,that it is reporting to the identified upstream aggregator. In anembodiment, the device begins reporting to an upstream aggregator andthe upstream aggregator uses the device's session token to report to alldownstream aggregators which are subordinate to the upstream aggregator,that the upstream aggregator is collecting data from the device. In anembodiment, the device checks in or registers with upstream aggregatorsusing the previously assigned session token but does not provide anindication of the downstream aggregator to which it was previouslyreporting data.

In an embodiment, each aggregator of the network periodically sendsmessages to IoT endpoint devices registered with the aggregatorreporting the current population of reporting devices. Each endpointdevice compares the current population data with its security thresholdvalue and determines is the threshold is satisfied. In situations wherethe threshold is no longer satisfied, the device stops reporting dataand searches upstream in the hierarchy for an aggregator havingsufficient reporting endpoints. As endpoint devices cease reporting toan aggregator, new messages are sent providing updated reportingpopulation information.

In an embodiment, reporting endpoints check the status of their currentaggregator by sending a message asking for a response. Aggregators whichhave gone offline do not respond causing the endpoints to cease sendingdata and to search upstream for an available aggregator. After findingand connecting with an upstream aggregator, the endpoints beginreporting data to the upstream aggregator. The endpoints can store databetween the time they cease and then resume reporting data, then sendingthe stored and current data to the new aggregator.

In an embodiment, downstream aggregators with no actively reportingendpoints, periodically send messages to the endpoint devices registeredwith the aggregator indicating the number of endpoints currentlyreporting to an upstream aggregator. If that number satisfies anendpoint's security threshold, the endpoint then responds to thedownstream aggregator that the endpoint is ready to move. The downstreamaggregator reports the number of “ready to move” responses to theendpoints which in turn begin reporting data to the downstreamaggregator after their respective security thresholds are satisfied bythe ready to move response number. This process can also be used as newaggregators are added to the network.

In an embodiment, the lowest level aggregators of the hierarchicalnetwork are issued anonymous credentials similar to those of theendpoint devices. In this embodiment, the endpoint devices registeranonymously with their local aggregator which in turn registersanonymously with an upstream aggregator. The lowest level aggregatorsevaluate the number of aggregators reporting to the upstream aggregatorsand report data from the endpoint devices when it is at or above thesecurity threshold of the lowest level aggregator. When the number isbelow the threshold, the lowest level aggregator stops reporting dataand evaluates aggregators further upstream until one with sufficientdata traffic is found. The lowest level aggregator then resumesreporting data to the new upstream aggregator. In this embodiment, theendpoint devices remain registered with the lowest level aggregator andcontinue to report data to that aggregator.

FIG. 1 provides a schematic illustration of exemplary network resourcesassociated with practicing the disclosed inventions. The inventions maybe practiced in the systems and processors of any of the disclosedelements which process an instruction stream. As shown in the figure, anetworked IoT endpoint device 104, connects wirelessly to serversub-system 102 via network 114. Client device 104 comprises dataaggregation program 175, together with sufficient computing resource(processor, memory, network communications hardware) to execute theprogram. Server sub-system 102 includes data aggregation program 175,and is representative of system data aggregators as well as thecentralized credential issuing element. As shown in FIG. 1, serversub-system 102 comprises a server computer 150. FIG. 1 depicts a blockdiagram of components of server computer 150 within a networked computersystem 1000, in accordance with an embodiment of the present invention.It should be appreciated that FIG. 1 provides only an illustration ofone implementation and does not imply any limitations with regard to theenvironments in which different embodiments can be implemented. Manymodifications to the depicted environment can be made.

Server computer 150 can include processor(s) 154, memory 158, persistentstorage 170, communications unit 152, input/output (I/O) interface(s)156 and communications fabric 140. Communications fabric 140 providescommunications between cache 162, memory 158, persistent storage 170,communications unit 152, and input/output (I/O) interface(s) 156.Communications fabric 140 can be implemented with any architecturedesigned for passing data and/or control information between processors(such as microprocessors, communications and network processors, etc.),system memory, peripheral devices, and any other hardware componentswithin a system. For example, communications fabric 140 can beimplemented with one or more buses.

Memory 158 and persistent storage 170 are computer readable storagemedia. In this embodiment, memory 158 includes random access memory(RAM) 160. In general, memory 158 can include any suitable volatile ornon-volatile computer readable storage media. Cache 162 is a fast memorythat enhances the performance of processor(s) 154 by holding recentlyaccessed data, and data near recently accessed data, from memory 158.

Program instructions and data used to practice embodiments of thepresent invention, e.g., the data aggregation program 175, are stored inpersistent storage 170 for execution and/or access by one or more of therespective processor(s) 154 of server computer 150 via cache 162. Inthis embodiment, persistent storage 170 includes a magnetic hard diskdrive. Alternatively, or in addition to a magnetic hard disk drive,persistent storage 170 can include a solid-state hard drive, asemiconductor storage device, a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM), a flash memory, or any othercomputer readable storage media that is capable of storing programinstructions or digital information.

The media used by persistent storage 170 may also be removable. Forexample, a removable hard drive may be used for persistent storage 170.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage170.

Communications unit 152, in these examples, provides for communicationswith other data processing systems or devices, including resources ofclient computing device 104. In these examples, communications unit 152includes one or more network interface cards. Communications unit 152may provide communications through the use of either or both physicaland wireless communications links. Software distribution programs, andother programs and data used for implementation of the presentinvention, may be downloaded to persistent storage 170 of servercomputer 150 through communications unit 152.

I/O interface(s) 156 allows for input and output of data with otherdevices that may be connected to server computer 150. For example, I/Ointerface(s) 156 may provide a connection to external device(s) 190 suchas a keyboard, a keypad, a touch screen, a microphone, a digital camera,and/or some other suitable input device. External device(s) 190 can alsoinclude portable computer readable storage media such as, for example,thumb drives, portable optical or magnetic disks, and memory cards.Software and data used to practice embodiments of the present invention,e.g., data aggregation program 175 on server computer 150, can be storedon such portable computer readable storage media and can be loaded ontopersistent storage 170 via I/O interface(s) 156. I/O interface(s) 156also connect to a display 180.

Display 180 provides a mechanism to display data to a user and may be,for example, a computer monitor. Display 180 can also function as atouch screen, such as a display of a tablet computer.

FIG. 2 provides a flowchart 200, illustrating exemplary activitiesassociated with the practice of the disclosure. After program start,anonymous credentials are issued to a plurality of devices by acentralized credentialing element portion of data aggregation program175 at 210. Credentialing can be distributed such that each low-levelaggregator issues credentials under the direction of the centralizedissuing element of data aggregation program 175 to prevent duplicationof credentials. In such an embodiment, the centralized issuing elementof data aggregation program 175 communicates the next availablecredentials and each low-level aggregating element checks outcredentials for each new endpoint connected to the network. Theanonymous credentials are received by new devices which then use thecredentials to register the devices at data aggregators under dataaggregation program 175 at 220. The data aggregation program 175provides each registered device with a session token. The registereddevices can communicate their security thresholds to the dataaggregation program 175 at registration. Data aggregation program 175then begins receiving data from the endpoint devices at 230. At 240 dataaggregation program 175 determines that the number of reporting endpointdevices at an aggregator is below a defined threshold. The determinationcan be made at the device after receiving a message from the localaggregator indicating the current reporting device population at theaggregator. The determination can be made at the aggregator afterevaluating the current reporting device population according to thesecurity thresholds of the reporting devices, and then communicated tothe reporting devices. After the determination, the reporting devicescheck in with an upstream aggregator to determine if the securitythreshold of the device is satisfied at that aggregator. At 250 dataaggregation program 175 registers the endpoint devices with an upstreamaggregator and the upstream aggregator begins receiving data from theendpoint devices at 260. The devices can be registered at allaggregators from their initial network interaction, in such anembodiment, the devices transfer from one aggregator to another andreport data to the latter aggregator after the transfer is complete.

FIG. 3 provides an illustration of the overall architecture 300, ofsystems of the invention. As shown in the figure, endpoint devices 310,in neighborhood 325 report data to downstream aggregator 335. Thesecurity threshold of endpoint devices 310 is 5 in this example.Endpoint devices 310 in neighborhoods 320 and 330, also have a securitythreshold of 5 and therefore report their data to upstream aggregator340. Downstream aggregators 322 and 332, are idle in the example asthere are less than the security thresholds of endpoint devices 310currently reporting in each of neighborhoods 320 and 330.

It is to be understood that although this disclosure includes a detaileddescription on cloud computing, implementation of the teachings recitedherein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported, providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure that includes anetwork of interconnected nodes.

Referring now to FIG. 4, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 includes one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 4 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 5, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 4) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 5 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture-based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may include applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and data aggregation program 175.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The invention may be beneficially practiced in any system, single orparallel, which processes an instruction stream. The computer programproduct may include a computer readable storage medium (or media) havingcomputer readable program instructions thereon for causing a processorto carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

References in the specification to “one embodiment”, “an embodiment”,“an example embodiment”, etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to affect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

For purposes of the description hereinafter, the terms “upper”, “lower”,“right”, “left”, “vertical”, “horizontal”, “top”, “bottom”, andderivatives thereof shall relate to the disclosed structures andmethods, as oriented in the Figures. The terms “overlying”, “atop”,“positioned on” or “positioned atop” mean that a first element, such asa first structure, is present on a second element, such as a secondstructure, wherein intervening elements, such as an interface structuremay be present between the first element and the second element. Theterm “direct contact” means that a first element, such as a firststructure, and a second element, such as a second structure, areconnected without any intermediary conducting, insulating orsemiconductor layers at the interface of the two elements.

The resulting integrated circuit chips can be distributed by thefabricator in raw wafer form (that is, as a single wafer that hasmultiple unpackaged chips), as a bare die, or in a packaged form. In thelatter case the chip is mounted in a single chip package (such as aplastic carrier, with leads that are affixed to a motherboard or otherhigher level carrier) or in a multichip package (such as a ceramiccarrier that has either or both surface interconnections or buriedinterconnections). In any case the chip is then integrated with otherchips, discrete circuit elements, and/or other signal processing devicesas part of either (a) an intermediate product, such as a motherboard, or(b) an end product. The end product can be any product that includesintegrated circuit chips, ranging from toys and other low-endapplications to advanced computer products having a display, a keyboardor other input device, and a central processor.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration but are not intended tobe exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A computer implemented method for managinganonymous network connections, the method comprising: providing, by oneor more computer systems, anonymous authentication credentials to aplurality of devices in a hierarchical network; registering, by the oneor more computer systems, a first set of devices of the plurality ofdevices with a first data aggregator; determining, by the one or morecomputer systems, that the first set of devices registered with thefirst data aggregator numbers less than a first threshold value; inresponse to the determining, registering, by the one or more computersystems, the first set of devices with a second data aggregator, whereinthe second data aggregator is upstream from the first data aggregator inthe hierarchical network; and wherein registering the first set ofdevices with the second data aggregator causes data from the first setof devices to be received at the second data aggregator.
 2. The computerimplemented method according to claim 1, further comprising:determining, by the one or more computer systems, that a second set ofdevices registered with the second data aggregator exceeds a secondthreshold value; and registering at least a portion of the second set ofdevices with the first data aggregator; wherein registering at least aportion of the second set of devices with the first data aggregatorcauses data from the portion of the second set of devices to be receivedat the first data aggregator.
 3. The computer implemented methodaccording to claim 1, wherein the authentication credentials relate toat least one of a location and a device class.
 4. The computerimplemented method according to claim 1, wherein the second dataaggregator covers a larger geographic area than the first dataaggregator.
 5. The computer implemented method according to claim 1,further comprising: ceasing to send updated aggregation population datafrom the first data aggregator; sending valid aggregation populationdata from a new data aggregator; and receiving data at the new dataaggregator.
 6. The computer implemented method according to claim 1,further comprising: providing, by the one or more computer systems, aregistry of session tokens associated with the plurality of devices,wherein the registry includes individual device identifiers encryptedusing a public key.
 7. The computer implemented method according toclaim 1, further comprising registering, by the one or more computersystems, devices at each level of a hierarchy.
 8. A computer programproduct for managing anonymous network connections, the computer programproduct comprising one or more computer readable storage devices andstored program instructions on the one or more computer readable storagedevices, the stored program instructions comprising: programinstructions for providing anonymous authentication credentials to aplurality of devices in a hierarchical network; program instructions forregistering devices at a first data aggregator; program instructions fordetermining that a first set of devices at the first data aggregator,numbers less than a first threshold value; program instructions forregistering the first set of devices with a second data aggregator inresponse to the determining, wherein the second data aggregator isupstream from the first data aggregator in the hierarchical network; andwherein registering the first set of devices with the second dataaggregator causes data from the first set of devices to be received atthe second data aggregator.
 9. The computer program product according toclaim 8, the stored program instructions further comprising: programinstructions for determining that a second set of devices registeredwith the second data aggregator exceeds a second threshold value; andprogram instructions for registering at least a portion of the secondset of devices with the first data aggregator; wherein registering atleast a portion of the second set of devices with the first dataaggregator causes data from the portion of the second set of devices tobe received at the first data aggregator.
 10. The computer programproduct according to claim 8, wherein the authentication credentialsrelate to at least one of a location and a device class.
 11. Thecomputer program product according to claim 8, wherein the second dataaggregator covers a larger geographic area than the first dataaggregator.
 12. The computer program product according to claim 8, thestored program instructions further comprising: program instructions forceasing to send updated aggregation population data from the first dataaggregator; program instructions for sending valid aggregationpopulation data from a new data aggregator; and program instructions forreceiving data at the new data aggregator.
 13. The computer programproduct according to claim 8, the stored program instructions furthercomprising: program instructions for providing a registry of sessiontokens associated with the plurality of devices, wherein the registryincludes individual device identifiers encrypted using a public key. 14.The computer program product according to claim 8, the stored programinstructions further comprising program instructions for registeringdevices at each level of a hierarchy.
 15. A computer system for managinganonymous network connections, the computer system comprising: one ormore computer systems; one or more computer readable storage devices;and stored program instructions on the one or more computer readablestorage devices for execution by the one or more computer systems, thestored program instructions comprising: program instructions forproviding anonymous authentication credentials to a plurality of devicesin a hierarchical network; program instructions for registering devicesat a first data aggregator; program instructions for determining that afirst set of devices at the first data aggregator, numbers less than afirst threshold value; program instructions for registering the firstset of devices with a second data aggregator in response to thedetermining, wherein the second data aggregator is upstream from thefirst data aggregator in the hierarchical network; and whereinregistering the first set of devices with the second data aggregatorcauses data from the first set of devices to be received at the seconddata aggregator.
 16. The computer system according to claim 15, thestored program instructions further comprising: program instructions fordetermining that a second set of devices registered with the second dataaggregator exceeds a second threshold value; and program instructionsfor registering at least a portion of the second set of devices with thefirst data aggregator; wherein registering at least a portion of thesecond set of devices with the first data aggregator causes data fromthe portion of the second set of devices to be received at the firstdata aggregator.
 17. The computer system according to claim 15, whereinthe authentication credentials relate to at least one of a location anda device class.
 18. The computer system according to claim 15, whereinthe second data aggregator covers a larger geographic area than thefirst data aggregator.
 19. The computer system according to claim 15,the stored program instructions further comprising: program instructionsfor ceasing to send, by the one or more computer systems, updatedaggregation population data from the first data aggregator; programinstructions for sending valid aggregation population data from a newdata aggregator; and program instructions for receiving data at the newdata aggregator.
 20. The computer system according to claim 15, thestored program instructions further comprising: program instructions forproviding a registry of session tokens associated with the plurality ofdevices, wherein the registry includes individual device identifiersencrypted using a public key.